IRIX Base Documentation 2002 November

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / u_man / cat1 / admin.z / admin

Wrap

Text File | 2002-10-03 | 18.7 KB | 397 lines

aaaaddddmmmmiiiinnnn((((1111)))) aaaaddddmmmmiiiinnnn((((1111)))) NNNNAAAAMMMMEEEE admin - create and administer SCCS files SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS aaaaddddmmmmiiiinnnn [----nnnn] [----iiii[name]] [----rrrr rel] [----tttt[name]] [----ffff flag[flag-val]][----dddd flag[flag-val]] [----aaaa login] [----eeee login] [----mmmm mmmmrrrrlllliiiisssstttt]]]] [[[[----yyyy[comment]] [----hhhh] [----zzzz] files DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _a_d_m_i_n is used to create new SCCS files and change parameters of existing ones. Arguments to _a_d_m_i_n, which may appear in any order, consist of keyletter arguments, which begin with ----, and named files (note that SCCS filenames must begin with the characters ssss....). If a named file does not exist, it is created and its parameters are initialized according to the specified keyletter arguments. Parameters not initialized by a keyletter argument are assigned a default value. If a named file does exist, parameters corresponding to specified keyletter arguments are changed and other parameters are left as is. If a directory is named, _a_d_m_i_n behaves as though each file in the directory were specified as a named file, except that non-SCCS files (last component of the pathname does not begin with ssss....) and unreadable files are silently ignored. If a name of ---- is given, the standard input is read; each line of the standard input is taken to be the name of an SCCS file to be processed. Again, non-SCCS files and unreadable files are silently ignored. OOOOPPPPTTTTIIIIOOOONNNNSSSS The keyletter arguments are as follows. Each is explained as though only one named file is to be processed because the effects of the arguments apply independently to each named file. ----nnnn This keyletter indicates that a new SCCS file is to be created. ----iiii[_n_a_m_e] The _n_a_m_e of a file from which the text for a new SCCS file is to be taken. The text constitutes the first delta of the file (see ----rrrr keyletter for delta numbering scheme). If the iiii keyletter is used but the filename is omitted, the text is obtained by reading the standard input until an end of Rused,file is encountered. If this keyletter is omitted, then the SCCS file is created empty. Only one SCCS file may be created by an _a_d_m_i_n command on which the iiii keyletter is supplied. Using a single _a_d_m_i_n to create two or more SCCS files requires that they be created empty (no ----iiii keyletter). Note that the ----iiii keyletter implies the ----nnnn keyletter. ----rrrr_r_e_l The _r_e_lease into which the initial delta is inserted. If the ----rrrr keyletter is not used, the initial delta is inserted into release 1. The level of the initial delta is always 1 (by default initial deltas are named 1.1). PPPPaaaaggggeeee 1111 aaaaddddmmmmiiiinnnn((((1111)))) aaaaddddmmmmiiiinnnn((((1111)))) ----tttt[_n_a_m_e] The _n_a_m_e of a file from which descriptive text for the SCCS file is to be taken. If the ----tttt keyletter is used and _a_d_m_i_n is creating a new SCCS file (the ----nnnn and/or ----iiii keyletters also used), the descriptive text filename must also be supplied. In the case of existing SCCS filesSflag ((((1111)))) aaaa ----tttt keyletter without a filename causes removal of descriptive text (if any) currently in the SCCS file, and (2) a ----tttt keyletter with a filename causes text (if any) in the named file to replace the descriptive text (if any) currently in the SCCS file. ----ffff_f_l_a_g This keyletter specifies a _f_l_a_g and, possibly, a value for the _f_l_a_g to be placed in the SCCS file. Several ffff keyletters may be supplied on a single _a_d_m_i_n command line. The allowable _f_l_a_gs and their values are bbbb Allows use of the ----bbbb keyletter on a _g_e_t(1) command to create branch deltas. cccc_c_e_i_l The highest release (i.e., ``ceiling''), a number greater than 0 but less than or equal to 9999, that can be retrieved by a _g_e_t(1) command for editing. The default value for an unspecified cccc flag is 9999. ffff_f_l_o_o_r The lowest release (i.e., ``floor''), a number greater than 0 but less than 9999, that can be retrieved by a _g_e_t(1) command for editing. The default value for an unspecified ffff flag is 1. dddd_S_I_D The default delta number (SIDs+1) used by a _g_e_t(1) command. iiii[_s_t_r] Causes the "No id keywords (ge6)" message issued by _g_e_t(1) or _d_e_l_t_a(1) to be treated as a fatal error. In the absence of this flag, the message is only a warning. The message is issued if no SCCS identification keywords (see _g_e_t(1)) are found in the text retrieved or stored in the SCCS file. If a value is supplied, the keywords must match the given string exactly; however, the string must contain a keyword and no embedded newlines. jjjj Allows concurrent _g_e_t(1) commands for editing on the same SIDs+1 of an SCCS file. This allows multiple concurrent updates to the same version of the SCCS file. llll_l_i_s_t A _l_i_s_t of releases to which deltas can no longer be made (ggggeeeetttt ----eeee against one of these ``locked'' releases fails). The _l_i_s_t has the following syntax: PPPPaaaaggggeeee 2222 aaaaddddmmmmiiiinnnn((((1111)))) aaaaddddmmmmiiiinnnn((((1111)))) <list> ::= <range> | <list> , <range> <range>~::= _R_E_L_E_A_S_E _N_U_M_B_E_R | aaaa The character aaaa in the _l_i_s_t is equivalent to specifying _a_l_l _r_e_l_e_a_s_e_s for the named SCCS file. nnnn Causes _d_e_l_t_a(1) to create a null delta in each of those releases (if any) being skipped when a delta is made in a _n_e_w release (e.g., in making delta 5.1 after delta 2.7, releases 3 and 4 are skipped). These null deltas serve as anchor points that branch deltas may later be created from. The absence of this flag causes skipped releases to be nonexistent in the SCCS file, preventing branch deltas from being created from them in the future. qqqq_t_e_x_t User definable text substituted for all occurrences of the %Q% keyword in the SCCS file text retrieved by _g_e_t(1). mmmm_m_o_d _M_o_dule name of the SCCS file substituted for all occurrences of the %M% keyword in the SCCS file text retrieved by _g_e_t(1). If the mmmm flag is not specified, the value assigned is the name of the SCCS file with the leading ssss.... removed. tttt_t_y_p_e _T_y_p_e of module in the SCCS file substituted for all occurrences of %Y% keyword in the SCCS file text retrieved by _g_e_t(1). vvvv_p_g_m Causes _d_e_l_t_a(1) to prompt for Modification Request (MR) numbers as the reason for creating a delta. The optional value specifies the name of an MR number validity checking program (see _d_e_l_t_a(1)). (If this flag is set when creating an SCCS file, the mmmm keyletter must also be used even if its value is null.) ----dddd_f_l_a_g Causes removal (deletion) of the specified _f_l_a_g from an SCCS file. The ----dddd keyletter may be specified only when processing existing SCCS files. Several ----dddd keyletters may be supplied on a single _a_d_m_i_n command. See the ----ffff keyletter for allowable _f_l_a_g names. llll_l_i_s_t A _l_i_s_t of releases to be ``unlocked.'' See the ----ffff keyletter for a description of the llll flag and the syntax of a _l_i_s_t. ----aaaa_l_o_g_i_n A _l_o_g_i_n name, or numeric UNIX system group ID, to be added to the list of users that make deltas (changes) to the SCCS file. A group ID is equivalent to specifying all _l_o_g_i_n names common to PPPPaaaaggggeeee 3333 aaaaddddmmmmiiiinnnn((((1111)))) aaaaddddmmmmiiiinnnn((((1111)))) that group ID. Several aaaa keyletters may be used on a single _a_d_m_i_n command line. As many _l_o_g_i_ns, or numeric group ID's as desired may be on the list simultaneously. If the list of users is empty, then anyone may add deltas. If a _l_o_g_i_n or group ID is preceded by a !!!! they are do not have permission to make deltas. ----eeee_l_o_g_i_n A _l_o_g_i_n name, or numeric group ID, to be erased from the list of users allowed to make deltas (changes) to the SCCS file. Specifying a group ID is equivalent to specifying all _l_o_g_i_n names common to that group ID. Several eeee keyletters may be used on a single _a_d_m_i_n command line. ----mmmm[_m_r_l_i_s_t] The list of Modification Requests (MR) numbers is inserted into the SCCS file as the reason for creating the initial delta in a manner identical to _d_e_l_t_a(1). The vvvv flag must be set and the MR numbers validated if the vvvv flag has a value (the name of an MR number validation program). Diagnostics will occur if the vvvv flag is not set or if MR validation fails. ----yyyy[_c_o_m_m_e_n_t] The _c_o_m_m_e_n_t text is inserted into the SCCS file as a comment for the initial delta in a manner identical to that of _d_e_l_t_a(1). Omissing the ----yyyy keyletter results in a default comment line being inserted in the form date and time created _Y_Y/_M_M/_D_D _H_H:_M_M:_S_S by _l_o_g_i_n The ----yyyy keyletter is valid only if the ----iiii and/or ----nnnn keyletters are specified (that is, a new SCCS file is being created). ----hhhh Causes _a_d_m_i_n to check the structure of the SCCS file (see _s_c_c_s_f_i_l_e(5)) and to compare a newly computed check-sum (the sum of all the characters in the SCCS file except those in the first line) with the check- sum that is stored in the first line of the SCCS file. Appropriate error diagnostics are produced. This keyletter inhibits writing on the file, nullifying the effect of any other keyletters supplied, and is, therefore, only meaningful when processing existing files. ----zzzz The SCCS file check-sum is recomputed and stored in the first line of the SCCS file (see ----hhhh, above). PPPPaaaaggggeeee 4444 aaaaddddmmmmiiiinnnn((((1111)))) aaaaddddmmmmiiiinnnn((((1111)))) Note that using this keyletter on a truly corrupted file may prevent future detection of the corruption. The last component of all SCCS filenames must be of the form ssss...._f_i_l_e_n_a_m_e. New SCCS files are given mode 444 (see _c_h_m_o_d(1)). Write permission in the pertinent directory is, of course, required to create a file. All writing done by _a_d_m_i_n is to a temporary x- file, called xxxx...._f_i_l_e_n_a_m_e (see _g_e_t(1)), created with mode 444 if the _a_d_m_i_n command is creating a new SCCS file or with the same mode as the SCCS file if it exists. After the successful execution of _a_d_m_i_n, the SCCS file is removed (if it exists) and the x-file is renamed with the name of the SCCS file. This ensures that changes are made to the SCCS file only if no errors occurred. It is recommended that directories containing SCCS files be mode 755 and that SCCS files themselves be mode 444. The mode of the directories allows only the owner to modify SCCS files contained in the directories. The mode of the SCCS files prevents any modification at all except by SCCS commands. If it should be necessary to patch an SCCS file for any reason, the mode may be changed to 644 by the owner allowing the use of _e_d(1). _C_a_r_e _m_u_s_t _b_e _t_a_k_e_n! The edited file should _a_l_w_a_y_s be processed by an _a_d_m_i_n ----hhhh to check for corruption, followed by an _a_d_m_i_n ----zzzz to generate a proper check-sum. Another _a_d_m_i_n ----hhhh is recommended to ensure the SCCS file is valid. _a_d_m_i_n also makes use of a transient lock file (called zzzz...._f_i_l_e_n_a_m_e), to prevent simultaneous updates to the SCCS file by different users. See _g_e_t(1) for further information. FFFFIIIILLLLEEEESSSS g-file Existed before the execution of _d_e_l_t_a; removed after completion of _d_e_l_t_a. p-file Existed before the execution of _d_e_l_t_a; may exist after completion of _d_e_l_t_a. q-file Created during the execution of _d_e_l_t_a; removed after completion of _d_e_l_t_a. x-file Created during the execution of _d_e_l_t_a; renamed to SCCS file after completion of _d_e_l_t_a. z-file Created during the execution of _d_e_l_t_a; removed during the execution of _d_e_l_t_a. d-file Created during the execution of _d_e_l_t_a; removed after completion of _d_e_l_t_a. /usr/bin/bdiff Program to compute differences between the ``gotten'' file and the _g-_f_i_l_e. SSSSEEEEEEEE AAAALLLLSSSSOOOO delta(1), ed(1), get(1), help(1), prs(1), what(1), sccsfile(4). PPPPaaaaggggeeee 5555 aaaaddddmmmmiiiinnnn((((1111)))) aaaaddddmmmmiiiinnnn((((1111)))) DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS Use _h_e_l_p(1) for explanations. PPPPaaaaggggeeee 6666